Repository navigation
docs(coding-agent): prepare source publication - #264
Merged
Merged
Conversation
- Restrict model publication to trusted main sources and isolate upload credentials - Disable unsafe issue analysis and update vulnerable production dependencies - Require an explicit retained-artifact audit before changing source visibility
This reverts commit 8e8ada3.
- Record disclosure evidence and the controlled visibility transition. - Preserve vendored license terms and clarify the approved publication scope.
- Preserve the merged README updates while retaining publication corrections. - Keep the follow-up review limited to new notices and audit documentation.
Pepps233
marked this pull request as ready for review
October 17, 2026 19:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare the source repository for a controlled public transition following the security fixes in #262.
Repository visibility remains private.
Reasoning
Public visibility exposes repository history and retained Actions evidence independently of npm distribution policy.
The disclosure review found no confirmed private Diffex credential, but two historical logs were unavailable and the review is not exhaustive.
Actions must be paused during transition until public protections are verified.
Changes
Testing
git diff --check.